Skip to content

feat: add HPA controller for workload deployments - #203

Open
savme wants to merge 2 commits into
feat/workloaddeployment-scale-subresourcefrom
feat/workloaddeployment-hpa-controller
Open

feat: add HPA controller for workload deployments#203
savme wants to merge 2 commits into
feat/workloaddeployment-scale-subresourcefrom
feat/workloaddeployment-hpa-controller

Conversation

@savme

@savme savme commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

This PR adds the cell-local autoscaling controller for WorkloadDeployment.

When a WorkloadDeployment has autoscaling enabled, the controller creates and keeps a matching HPA up to date. The HPA stays local to the cell and is not propagated through karmada. This uses the existing CPU and memory metric settings for configuration.

Note that Resource metrics still need to be served for pods created by kraftlet. This will be added in a follow-up.

Related to datum-cloud/enhancements#799

@savme
savme requested a review from scotwells August 3, 2026 17:02
scotwells
scotwells previously approved these changes Aug 3, 2026

@scotwells scotwells left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@savme can we add a chainsaw end to end test to validate this behavior? I think for this we can just validate that the HPA is lifecycle correctly based on auto-scale settings.

Longer-term we need to think about how we can validate auto-scaling behavior in CI so we can confirm that custom metrics we export for instances can trigger auto-scaling.

@savme
savme force-pushed the feat/workloaddeployment-hpa-controller branch from 4517f0d to 77e6dca Compare August 4, 2026 13:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants